Hey Greg, nice to hear from you. Just to make sure we're on the same page, lock_import doesn't exist anymore in v2 (see the migration note here). Are you all using v2, or v1 still?

We're on v1 and this was one patch we can ditch before upgrade to v2.

I probably should have looked at the v2 code first! 🤣

What's the nearest equivalent? Or is there no such thing in v2? Is the intent clear of what we're looking for?

There's still lock importing in v2, but it looks more like:

uv = use_extension("@rules_pycross//pycross/extensions:uv.bzl", "uv")
uv.workspace(
    name = "pypi",
    lock_file = "//:uv.lock",
)
uv.repo(
    workspace = "pypi",
)
uv.package(
    name = "numpy",
    always_build = True,
    workspace = "pypi",  # was: repo = "pypi"
)

(sub uv for pdm, poetry, etc.)

And there's still a //_lock, but it's in a mostly hidden "workspace" repository now. That workspace repository contains all of the packages in the lock, and then the actual pypi repository is some subset of those (only pinned packages, only packages from one workspace member project, etc.).

I think that's the largest conflict with this patch; it seems like it would work, but would require users to use that hidden workspace repo to access it, fighting with bazel mod tidy, etc.